Repository navigation
Conversation
Named collection or backup disk with from_env, so BACKUP/RESTORE statements carry no S3 keys, and the grants a dedicated backup user needs: NAMED COLLECTION from 25.8, WRITE/READ ON S3 or ON DISK from 26.8.
Contributor
|
All contributors have signed the CLA ✍️ ✅ |
Author
|
I have read the CLA Document and I hereby sign the CLA |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The KB covers clickhouse-backup but has no page on native
BACKUP/RESTOREto S3. This adds one on keeping the S3 keys out of the statements (named collection or backup disk, both withfrom_env) and on the grants a dedicated backup user needs, which changed in 25.8 and again in 26.8 LTS.Tested (Docker, S3-compatible store), every SQL and XML block copied from the article:
count()andsum(cityHash64(*))equal to the source: 24.8.14, 26.10.4; also 25.3.14, 25.8.33, Altinity Stable 25.3.14.10003 (from_env)BACKUP, SELECT ON db.*:NAMED COLLECTION ON <name>;Disk()needs nothing moreWRITE ON S3/WRITE ON DISK; restore needsREAD ON S3system.named_collectionsshows[HIDDEN]for all values on every version aboveThe 25.8 boundary for
NAMED COLLECTION ON <name>comes from these tests; I did not find the changelog entry for it, so a pointer is welcome.Sources: #94605 (SQL-defined named collections in BACKUP/RESTORE, 26.1 + backports), #114405 (SOURCES grants for backup locations, 26.8), #117406 (
Disk()authorization,READ/WRITE ON DISK).I have read the CLA Document and I hereby sign the CLA